Handover method and apparatus

ABSTRACT

A handover method includes: transmitting a handover request message by a source base station to a target base station when a user equipment (UE) is being handed over from the source base station to the target base station, where the handover request message carries one or more DRB information items configured by the source base station for the UE and one or more flow QoS information items configured by a core network side for the UE; receiving, by the source base station, a handover request acknowledgement message transmitted by the target base station, where the handover request acknowledgement message carries first DRB configuration information generated by the target base station for the UE; and transmitting an RRC connection reconfiguration message carrying the first DRB configuration information by the source base station to the UE. Also disclosed is a handover apparatus.

TECHNICAL FIELD

The present disclosure relates to the communications field and, inparticular, to a handover method and apparatus.

BACKGROUND

FIG. 1 is a structural diagram of a 4G system. In the 4th Generation(4G) or the Long Term Evolution (LTE) mobile communication system, dataflows with the same Quality of Service (QoS) requirement are aggregatedinto a bearer. An access network (AN) and a core network (CN) processthe QoS according to the bearer. In the 4G system, the access networkincludes an evolved Node B (eNB) and a user equipment (UE). If onenetwork side bearer on an S1 interface between the eNB and the corenetwork exists, one radio bearer on an air interface between the eNB andthe UE correspondingly exists. That is, the network side bearer and theradio bearer are in one-to-one correspondence.

In the 4G system, a QoS parameter includes: a QoS class identifier (QCI)and an allocation and retention priority (ARP). The QCI includes abearer type (a guaranteed bit rate (GBR) or a non-GBR), a priority, apacket delay budget and a packet error Rate. The APR is configured toindicate a priority of the bearer corresponding to deleting or retainingwhen an overload occurs.

If the bearer type is a non-GBR bearer, the QoS parameter furtherincludes: an aggregate maximum bit rate (AMBR). The AMBR includes:aggregate maximum bit rates of all non-GBR bearers of the UE (UE-AMBR)and an aggregate maximum bit rate of a non-GBR bearer corresponding toan access point name (APN) (APN-AMBR).

If the bearer type is a GBR bearer, the QoS parameter further includes:a maximum bit rate (MBR) and a GBR.

In the 4G system, since a QoS policy is controlled by the core networkand the base station passively accepts or rejects the QoS parameter, thebase station cannot adjust the QoS parameter according to a real-timewireless load and the core network cannot learn the current wirelessload in real time. Therefore, it is difficult for the core network tomake a reasonable QoS decision. A policy and charging rule function(PCRF) in the core network ensures that the UE does not have two bearersof the same QoS in a packet data network (PDN) link. After the UErequested a first PDN link, if the UE requests a second PDN link, abearer having the same QoS as that in the first PDN link may beestablished due to different PCRF decisions, and a UE may have twonetwork side bearers of the same QoS. Since the radio bearer and thenetwork side bearer are in one-to-one correspondence, multiple radiobearers exist, causing the waste of the radio resources.

FIG. 2 is a structural diagram of a 5th Generation (5G) system using the5G mobile communication technology. Compared with the 4G mobilecommunication system, the 5G mobile communication system may have animproving demand for 1000 times network throughput capacity, 100 timesdevice connections and one tenth lower latency. To a certain extent, the5G system requires a new and better QoS mechanism.

The 5G system may adopt a unified structure to support an enhancedmobile broadband (eMBB), massive machine type communication (mMTC),ultra reliable and low latency communication (URLLC) and other services.In the 5G system, the core network, the base station and the UE may begreatly evolved. A base station for the transition from the 4G mobilecommunication technology to the 5G mobile communication technology mayexist. An air interface of this type of base station is similar to anair interface of the base station (i.e., eNB) in the 4G system, and thistype of base station may be successfully connected to a 5G core networkvia its air interface. This type of base station may be referred to asan evolved eNB. Similar to an X2 interface between eNBs in the 4Gsystem, a direct interface may also exist between 5G base stations inthe 5G system, which is referred to as an Xn interface. The Xn interfacemay also exist between evolved eNBs or between the evolved eNB and the5G base station. Similar to an S1 interface between the eNB and the corenetwork in the 4G system, an interface between the 5G base station andthe 5G core network in the 5G system is referred to as an NG interface.The NG interface may also exist between the evolved eNB and the 5G corenetwork.

The evolved eNB may also be successfully connected to the 5G corenetwork, but since the evolved eNB is similar to the base station (eNB)in the 4G system on the aspect of the air interface, a radio resourcecontrol (RRC) protocol of the evolved eNB is similar to the RRC of theeNB, which is significantly different from the RRC of the 5G basestation. Therefore, the evolved eNB and the 5G base station may not beable to identify each other's RRC protocol.

SUMMARY

A handover method and apparatus provided by the present disclosure maysolve the problem that the QoS mechanism adopted by a core network andthe QoS mechanism adopted by an access network are different when thebase station is being handed over.

A handover method includes:

transmitting a handover request message by a source base station to atarget base station when a user equipment (UE) is being handed over fromthe source base station to the target base station, where the handoverrequest message carries one or more DRB information items configured bythe source base station for the UE and one or more flow QoS informationitems configured by a core network side for the UE;

receiving, by the source base station, a handover requestacknowledgement message transmitted by the target base station, wherethe handover request acknowledgement message carries first DRBconfiguration information generated by the target base station for theUE according to the handover request message; and

transmitting a radio resource control (RRC) connection reconfigurationmessage carrying the first DRB configuration information by the sourcebase station to the UE, where the first DRB configuration information isused for configuring radio resources by the UE.

In an exemplary embodiment, the flow QoS information item includes:identifier information for indicating the flow quality of serviceinformation item and a quality of service (Qos) rule. The identifierinformation includes a flow identifier or a quality of serviceidentifier (QoS ID).

In an exemplary embodiment, the QoS rule includes at least one of thefollowing: a packet delay budget (PDB), a packet error rate (PER), apriority, a guaranteed flow bit rate, a maximum flow bit rate, anallocation and retention priority, a per UE maximum bit rate, admissioncontrol, a flow priority level (FPL), a packet priority instruction(PPI), a packet discard priority indicator (PDPI), a quality ofexperience (QoE) level, and a reflective QoS indication.

In an exemplary embodiment, each DRB information item includes: a DRBidentifier (DRB ID); and

the each DRB information item further includes: the flow ID associatedwith the DRB corresponding to the DRB ID or the QoS ID associated withthe DRB corresponding to the DRB ID, and second DRB configurationinformation configured by the source base station for the DRB. Thesecond DRB configuration information includes a packet data convergenceprotocol (PDCP), a radio link control (RLC) and a configurationparameter of a logical channel, which are configured by the source basestation for the DRB.

In an exemplary embodiment, when the first DRB configuration informationreceived by the source base station includes a flow ID or QoS ID that isnot associated with any DRB in the one or more DRB information items,after the source base station transmits the RRC connectionreconfiguration message to the UE, the method further includes:

transmitting the flow ID or QoS ID that is not associated with any DRBin the one or more DRB information items by the source base station to acore network.

A handover method includes:

receiving, by a target base station, a handover request messagetransmitted by a source base station when a user equipment (UE) is beinghanded over from the source base station to the target base station,where the handover request message carries one or more DRB informationitems configured by the source base station for the UE and one or moreflow QoS information items configured by a core network side for the UE;

generating first DRB configuration information by the target basestation for the UE according to the handover request message; and

transmitting a handover request acknowledgement message carrying thefirst DRB configuration information by the target base station to thesource base station.

In an exemplary embodiment, the generating first DRB configurationinformation by the target base station for the UE according to thehandover request message includes:

putting, by the target base station, DRB configuration informationcorresponding to a first DRB in the one or more DRB information itemswhich the target base station agrees to establish into a DRB additionmodification list, and putting a DRB identifier corresponding to asecond DRB in the one or more DRB information items which the targetbase station does not agree to establish into a DRB release list; and

determining, by the target base station, the DRB addition modificationlist and the DRB release list to be the first DRB configurationinformation.

In an exemplary embodiment, each DRB configuration information in theDRB addition modification list includes a first DRB ID and one or moreof the following: one or more flow IDs or quality of service identifiers(QoS IDs) associated with a first DRB corresponding to the first DRB ID,packet data convergence protocol (PDCP) configuration information, radiolink control (RLC) configuration information and logical channelconfiguration information.

In an exemplary embodiment, the one or more flow IDs or QoS IDsassociated with the first DRB corresponding to the first DRB IDincludes: one or more flow IDs or QoS IDs with which the first DRB isre-associated after the target base station changes an associationrelationship between the first DRB and the one or more flow IDs or QoSIDs.

In an exemplary embodiment, when the first DRB configuration informationincludes a flow ID or QoS ID that is not associated with any DRB in theone or more DRB information items, after the UE successfully accesses tothe target base station, the method further includes:

transmitting the flow ID or QoS ID that is not associated with any DRBin the one or more DRB information items by the target base station to acore network.

A handover method includes:

receiving, by a user equipment (UE), a radio resource control (RRC)connection reconfiguration message carrying DRB configurationinformation transmitted by a source base station when the UE is beinghanded over from the source base station to the target base station,where the DRB configuration information is generated by the target basestation for the UE according to a handover request message, and thehandover request message is transmitted by the source base station tothe target base station and carries one or more DRB information itemsconfigured by the source base station for the UE and one or more flowQoS information items configured by a core network side for the UE; and

configuring, by the UE, radio resources according to the DRBconfiguration information in the RRC connection reconfiguration message.

In an exemplary embodiment, the DRB configuration information includes:a DRB addition modification list and a DRB release list.

Each tuple in the DRB addition modification list comprises a first DRBidentifier and one or more of: one or more flow IDs or quality ofservice identifiers (QoS IDs) associated with a first DRB correspondingto the first DRB identifier, packet data convergence protocol (PDCP)configuration information, radio link control (RLC) configurationinformation and logical channel configuration information, where thefirst DRB is a DRB in the one or more DRB information items which thetarget base station agrees to establish.

Each tuple in the DRB release list comprises a second DRB ID, where asecond DRB corresponding to the second DRB ID is a DRB in the one ormore DRB information items which the target base station does not agreeto establish.

In an exemplary embodiment, the configuring, by the UE, radio resourcesaccording to the DRB configuration information in the RRC connectionreconfiguration message includes:

configuring, by the UE, radio resources for the first DRB according toeach tuple information in the DRB addition modification list; and

releasing radio resources of the second DRB corresponding to the secondDRB ID according to the second DRB ID in each tuple information in theDRB release list.

In an exemplary embodiment, the configuring radio resources on the firstDRB includes one or more of the following:

reestablishing PDCP;

reestablishing RLC;

reconfiguring the PDCP according to the PDCP configuration information;

reconfiguring the RLC according to the RLC configuration information;

reconfiguring a logical channel according to the logical channelconfiguration information; and

reconfiguring an association relationship between the first DRB and theflow ID or QoS ID according to the flow ID or QoS ID associated with thefirst DRB.

A handover apparatus, which is applied to a source base station,includes: a first transmission module, a reception module and a secondtransmission module.

The first transmission module is configured to transmit a handoverrequest message to a target base station when a user equipment (UE) isbeing handed over from the source base station to the target basestation. The handover request message carries one or more DRBinformation items configured by the source base station for the UE andone or more flow QoS information items configured by a core network sidefor the UE.

The reception module is configured to receive a handover requestacknowledgement message transmitted by the target base station. Thehandover request acknowledgement message carries first DRB configurationinformation generated by the target base station for the UE according tothe handover request message.

The second transmission module is configured to transmit a radioresource control (RRC) connection reconfiguration message carrying thefirst DRB configuration information to the UE. The first DRBconfiguration information is used for configuring radio resources by theUE.

In an exemplary embodiment, the flow quality of service information itemincludes: identifier information for indicating the flow quality ofservice information item and a quality of service rule, where theidentifier information includes a flow identifier or a quality ofservice identifier (QoS ID).

A handover apparatus, which is applied to a target base station,includes: a reception module, a generation module and a transmissionmodule.

The reception module is configured to receive a handover request messagetransmitted by a source base station when a UE is being handed over fromthe source base station to the target base station. The handover requestmessage carries one or more DRB information items configured by thesource base station for the UE and one or more flow QoS informationitems configured by a core network side for the UE.

The generation module is configured to generate first DRB configurationinformation for the UE according to the handover request message.

The transmission module is configured to transmit a handover requestacknowledgement message carrying the first DRB configuration informationto the source base station.

In an exemplary embodiment, the generation module includes: aconfiguration unit and a determination unit.

The configuration unit is configured to put DRB configurationinformation corresponding to a first DRB in the one or more DRBinformation items which the target base station agrees to establish intoa DRB addition modification list, and put a DRB identifier correspondingto a second DRB in the one or more DRB information items which thetarget base station does not agree to establish into a DRB release list.

The determination unit is configured to determine the DRB additionmodification list and the DRB release list to be the first DRBconfiguration information.

A handover apparatus, which is applied to a user equipment (UE),includes: a reception module and a configuration module.

The reception module is configured to receive a radio resource control(RRC) connection reconfiguration message carrying DRB configurationinformation transmitted by a source base station when the UE is beinghanded over from the source base station to a target base station. TheDRB configuration information is generated by the target base stationfor the UE according to a handover request message. The handover requestmessage is transmitted by the source base station to the target basestation and carries one or more DRB information items configured by thesource base station for the UE and one or more flow QoS informationitems configured by a core network side for the UE.

The configuration module is configured to configure radio resourcesaccording to the DRB configuration information in the RRC connectionreconfiguration message.

In an exemplary embodiment, the DRB configuration information includes:a DRB addition modification list and a DRB release list.

Each tuple in the DRB addition modification includes a first DRBidentifier and one or more of: one or more flow IDs or quality ofservice identifiers (QoS IDs) associated with a first DRB correspondingto the first DRB identifier, packet data convergence protocol (PDCP)configuration information, radio link control (RLC) configurationinformation and logical channel configuration information, where thefirst DRB is a DRB in the one or more DRB information items which thetarget base station agrees to establish.

Each tuple in the DRB release list includes a second DRB ID, wherein asecond DRB corresponding to the second DRB ID is a DRB in the one ormore DRB information items which the target base station does not agreeto establish.

A computer-readable storage medium stores computer-executableinstructions for executing any method described above. A source basestation includes:

at least one processor; and

a memory which is communicatively connected to the at least oneprocessor.

The memory stores instructions which may be executed by the at least oneprocessor, and the at least one processor executes the instructions toexecute the above method executed by the source base station.

A target base station includes:

at least one processor; and

a memory which is communicatively connected to the at least oneprocessor.

The memory stores instructions which may be executed by the at least oneprocessor, and the at least one processor executes the instructions toexecute the above method executed by the target base station.

A user equipment includes:

at least one processor; and

a memory which is communicatively connected to the at least oneprocessor.

The memory stores instructions which may be executed by the at least oneprocessor, and the at least one processor executes the instructions toexecute the above method executed by the user equipment.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a structural diagram of a 4G system;

FIG. 2 is a structural diagram of a 5G system;

FIG. 3 is a flowchart of a handover method according to an embodiment ofthe present disclosure;

FIG. 4 is a flowchart of another handover method according to anembodiment of the present disclosure;

FIG. 5 is a flowchart of yet another handover method according to anembodiment of the present disclosure;

FIG. 6 is a block diagram of a handover apparatus according to anembodiment of the present disclosure;

FIG. 7 is a block diagram of another handover apparatus according to anembodiment of the present disclosure;

FIG. 8 is a block diagram of yet another handover apparatus according toan embodiment of the present disclosure;

FIG. 9 is a flowchart of a handover method according to an embodiment ofthe present disclosure;

FIG. 10 is a schematic diagram illustrating a hardware structure of asource base station according to an embodiment of the presentdisclosure;

FIG. 11 is a schematic diagram illustrating a hardware structure of atarget base station according to an embodiment of the presentdisclosure; and

FIG. 12 is a schematic diagram illustrating a hardware structure of auser equipment according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

The terms “first”, “second” and the like in the description, claims anddrawings of the present disclosure are used to distinguish betweensimilar objects and are not necessarily used to describe a particularorder or sequence. FIG. 3 is a flowchart of a handover method accordingto an embodiment of the present disclosure. The method provided by thisembodiment may be used in the network structure shown in FIG. 1 or FIG.2 described above. The execution party of the method in this embodimentmay be a base station, for example, a source base station. As shown inFIG. 3, the method includes the steps described below.

In step 302, a source base station transmits a handover request messageto a target base station when a user equipment (UE) is being handed overfrom the source base station to the target base station, where thehandover request message carries one or more data radio bearer (DRB)information items configured by the source base station for the UE andone or more flow quality of service (Qos) information items configuredby a core network side for the UE.

In step 304, the source base station receives a handover requestacknowledgement message transmitted by the target base station. Thehandover request acknowledgement message carries first DRB configurationinformation generated by the target base station for the UE according tothe handover request message.

In step 306, the source base station transmits a radio resource control(RRC) connection reconfiguration message carrying the first DRBconfiguration information to the UE, where the first DRB configurationinformation is used for being configured radio resources by the UE.

The method described above may solve the problem that the QoS mechanismadopted by a core network and the QoS mechanism adopted by an accessnetwork are not unified in the base station handover. When the corenetwork and the access network adopt different QoS mechanisms and anevolved eNB and a 5G base station cannot identify each other's RRCprotocol, the method described above may implement the handover on an Xninterface between the evolved eNB and the 5G base station which canensure the QoS (e.g., no data packet is lost and no data packet isrepeatedly transmitted).

Optionally, the flow QoS information item includes: identifierinformation for indicating the flow QoS information item and a QoS rule,where the identifier information includes a flow identifier or a QoS ID.

In an embodiment, the QoS rule includes at least one of the following: apacket delay budget (PDB), a packet error rate (PER), a priority, aguaranteed flow bit rate, a maximum flow bit rate, an allocation andretention priority (ARP), a per UE maximum bit rate, admission control,a flow priority level (FPL), a packet priority instruction (PPI), apacket discard priority indicator (PDPI), a quality of experience (QoE)level (QoS Level), and a reflective QoS indication.

The reflective QoS indication is used for indicating that uplink flowQoS information is determined according to downlink flow QoSinformation. When the QoS rule includes the reflective QoS indication,the QoS rule may not include the uplink flow QoS information.

In an exemplary embodiment, each DRB information item includes: a DRBID. The DRB information item further includes: the flow ID associatedwith a DRB corresponding to the DRB ID or the QoS ID associated with theDRB corresponding to the DRB ID, and second DRB configurationinformation configured by the source base station for the DRB. Thesecond DRB configuration information includes: a packet data convergenceprotocol (PDCP), radio link control (RLC) and a configuration parameterof a logical channel, which are configured by the source base stationfor the DRB.

In an exemplary embodiment, if the first DRB configuration informationreceived by the source base station includes a flow ID or QoS ID that isnot associated with any of all DRBs corresponding to all DRBs in all DRBinformation items, after the source base station transmits the RRCconnection reconfiguration message to the UE, the method furtherincludes: transmitting the flow ID or QoS ID that is not associated withany of all DRBs corresponding to all DRBs in all DRB information itemsby the source base station to a core network.

FIG. 4 is a flowchart of a handover method according to an embodiment ofthe present disclosure. As shown in FIG. 4, the method includes stepsdescribed below.

In step 402, when a user equipment (UE) is being handed over from asource base station to a target base station, the target base stationreceives a handover request message transmitted by the source basestation. The handover request message carries one or more DRBinformation items configured by the source base station for the UE andone or more flow QoS information items configured by a core network sidefor the UE.

In step 404, the target base station generates first DRB configurationinformation for the UE according to the handover request message.

In step 406, the target base station transmits a handover requestacknowledgement message carrying the first DRB configuration informationto the source base station.

In an exemplary embodiment, the process of generating first DRBconfiguration information by the target base station for the UEaccording to the handover request message includes:

putting, by the target base station, DRB configuration informationcorresponding to a first DRB in the DRB information items which thetarget base station agrees to establish into a DRB addition modificationlist, and putting a DRB ID corresponding to a second DRB in the DRBinformation items which the target base station does not agree toestablish into a DRB release list; and

determining, by the target base station, the DRB addition modificationlist and the DRB release list to be the first DRB configurationinformation.

In an exemplary embodiment, each DRB configuration information in theDRB addition modification list includes a first DRB ID and one or moreof the following: one or more flow IDs or QoS IDs associated with a DRBcorresponding to the first DRB ID, packet data convergence protocol(PDCP) configuration information, radio link control (RLC) configurationinformation and logical channel configuration information.

In an exemplary embodiment, the one or more flow IDs or QoS IDsassociated with a first DRB corresponding to the first DRB ID includes:one or more flow IDs or QoS IDs with which the first DRB correspondingto the first DRB ID is re-associated after the target base stationchanges an association relationship between the first DRB and the one ormore flow IDs or QoS IDs.

In an optional embodiment, if the DRB configuration information includesa flow ID or QoS ID that is not associated with any DRB in all DRBinformation items, after the UE successfully accesses to the target basestation, the method further includes: transmitting the flow ID or QoS IDthat is not associated with any DRB in all DRB information items by thesource base station to a core network.

FIG. 5 is a flowchart of a handover method according to an embodiment ofthe present disclosure. As shown in FIG. 5, the method includes stepsdescribed below.

In step 502, when a user equipment (UE) is being handed over from asource base station to a target base station, the UE receives a radioresource control (RRC) connection reconfiguration message carrying DRBconfiguration information transmitted by the source base station. TheDRB configuration information is generated by the target base stationfor the UE according to a handover request message, and the handoverrequest message is transmitted by the source base station to the targetbase station and carries one or more DRB information items configured bythe source base station for the UE and one or more flow QoS informationitems configured by a core network side for the UE.

In step 504, the UE configures radio resources according to the DRBconfiguration information in the RRC connection reconfiguration message.

In an exemplary embodiment, the DRB configuration information includes:a DRB addition modification list and a DRB release list. Each tuple inthe DRB addition modification list includes a first DRB ID and one ormore of the following: one or more flow IDs or QoS IDs associated with afirst DRB corresponding to the first DRB ID, PDCP configurationinformation, RLC configuration information and logical channelconfiguration information. The first DRB is a DRB in the DRB informationitems which the target base station agrees to establish. Each tuple inthe DRB release list includes a second DRB ID, and the second DRBcorresponding to the second DRB ID is a DRB in the DRB information itemswhich the target base station does not agree to establish.

In an exemplary embodiment, the process of the UE configuring radioresources according to the DRB configuration information in the RRCconnection reconfiguration message includes: configuring, by the UE,radio resources for the first DRB according to each tuple information inthe DRB addition modification list, and releasing radio resources of thesecond DRB corresponding to the second DRB ID according to the secondDRB ID in the each tuple information in the DRB release list.

In an exemplary embodiment, the configuring radio resources for thefirst DRB includes one or more of the following:

reestablishing PDCP;

reestablishing RLC;

reconfiguring the PDCP according to the PDCP configuration information;

reconfiguring the RLC according to the RLC configuration information;

reconfiguring a logical channel according to the logical channelconfiguration information; and

reconfiguring an association relationship between the first DRB and theflow ID or QoS ID according to the flow ID or QoS ID associated with thefirst DRB.

The method in embodiments described above may be implemented by softwareplus a general-purpose hardware platform, or may be implemented byhardware. The solution provided by the present disclosure may beembodied in the form of a software product. The computer softwareproduct is stored in a non-transient storage medium (such as a read-onlymemory (ROM), a random-access memory (RAM), a magnetic disk or anoptical disk) and the computer software product includes one or moreinstructions for enabling a terminal device (which may be a mobilephone, a computer, a server, a network device or the like) to executethe method described in the embodiments of the present disclosure. Thecomputer software product may be stored in a transient storage medium.

The following embodiments of the present disclosure provide handoverapparatuses for implementing the embodiments described above. A term“module” may be at least one of software and hardware capable ofimplementing preset functions.

FIG. 6 is a block diagram of a handover apparatus according to anembodiment of the present disclosure. The apparatus may be applied in asource base station. As shown in FIG. 6, the apparatus includes: a firsttransmission module 60, a reception module 62 and a second transmissionmodule 64.

The first transmission module 60 is configured to transmit a handoverrequest message to a target base station when a user equipment (UE) isbeing handed over from the source base station to the target basestation. The handover request message carries one or more DRBinformation items configured by the source base station for the UE andone or more flow QoS information items configured by a core network sidefor the UE.

The reception module 62 is configured to receive a handover requestacknowledgement message transmitted by the target base station. Thehandover request acknowledgement message carries first DRB configurationinformation generated by the target base station for the UE according tothe handover request message.

The second transmission module 64 is configured to transmit a radioresource control (RRC) connection reconfiguration message carrying thefirst DRB configuration information to the UE, where the first DRBconfiguration information is used by the UE for configuring radioresources.

In an exemplary embodiment, the flow quality of service informationincludes: identifier information for indicating the flow quality ofservice information and a quality of service rule, where the identifierinformation includes a flow identifier or a QoS ID.

FIG. 7 is a block diagram of a handover apparatus according to anembodiment of the present disclosure. The apparatus may be applied in atarget base station. As shown in FIG. 7, the apparatus includes: areception module 70, a generation module 72 and a transmission module74.

The reception module 70 is configured to receive a handover requestmessage sent by the target base station when a user equipment (UE) isbeing handed over from a source base station to the target base station.The handover request message carries one or more DRB information itemsconfigured by the source base station for the UE and one or more flowQoS information items configured by a core network side for the UE.

The generation module 72 is configured to generate first DRBconfiguration information for the UE according to the handover requestmessage.

The transmission module 74 is configured to transmit a handover requestacknowledgement message carrying the first DRB configuration informationto the source base station.

In an exemplary embodiment, the generation module 72 includes: aconfiguration unit and a determination unit. The configuration unit isconfigured to put DRB configuration information corresponding to a firstDRB in the DRB information items which the target base station agrees toestablish into a DRB addition modification list, and put a DRBidentifier corresponding to a second DRB in the DRB information itemswhich the target base station does not agree to establish into a DRBrelease list. The determination unit is configured to determine the DRBaddition modification list and the DRB release list to be the first DRBconfiguration information.

FIG. 8 is a block diagram of a handover apparatus according to anembodiment of the present disclosure. The apparatus may be applied in auser equipment (UE). As shown in FIG. 8, the apparatus includes: areception module 80 and a configuration module 82.

The reception module 80 is configured to receive a radio resourcecontrol (RRC) connection reconfiguration message carrying DRBconfiguration information transmitted by a source base station when theUE is being handed over from the source base station to a target basestation. The DRB configuration information is generated by the targetbase station for the UE according to a handover request message. Thehandover request message is transmitted by the source base station tothe target base station and carries one or more DRB information itemsconfigured by the source base station for the UE and one or more flowQoS information items configured by a core network side for the UE.

The configuration module 82 is configured to configure radio resourcesaccording to the DRB configuration information in the RRC connectionreconfiguration message.

In an exemplary embodiment, the DRB configuration information of thetarget base station for the UE includes: a DRB addition modificationlist and a DRB release list. Each tuple in the DRB addition modificationlist includes a first DRB identifier and one or more of the following:one or more flow IDs or QoS IDs associated with a first DRBcorresponding to the first DRB ID, packet data convergence protocol(PDCP) configuration information, radio link control (RLC) configurationinformation and logical channel configuration information, where thefirst DRB is a DRB in the DRB information items which the target basestation agrees to establish.

Each tuple in the DRB release list includes a second DRB ID, where asecond DRB corresponding to the second DRB ID is a DRB in the DRBinformation items which the target base station does not agree toestablish.

The various modules described above may be implemented by software orhardware. In the implementation by hardware, the various modules aredisposed in a same processor or respectively in processors in a mannerthat the various modules may be combined arbitrarily.

An embodiment of the present disclosure provides a handover method foran Xn interface to ensure the QoS. The method includes the stepsdescribed below.

A source base station transmits a handover request message to a targetbase station. The handover request message carries one or more DRBinformation items of a source base station at an access network side(i.e., the DRB information item configured by the source base stationfor the UE described in the above embodiment) and one or more flow QoSinformation items configured by a core network side for the UE.

The target base station receives the handover request message, agreesthe handover request and generates first DRB configuration informationaccording to information carried by the handover request message.

The target base station transmits a handover request acknowledgementmessage to the source base station. The handover request acknowledgementmessage carries the first DRB configuration information. The source basestation receives the handover request acknowledgement message andtransmits an RRC connection reconfiguration message to the UE. The RRCconnection reconfiguration message carries DRB configuration informationof the target base station. The UE receives the RRC connectionreconfiguration message and performs the configuration according to thefirst DRB configuration information.

FIG. 9 is a flowchart of a handover method according to an embodiment ofthe present disclosure. In this embodiment, the target base stationagrees to establish DRBs in all DRB information items, and the methodincludes steps described below.

In step 1, the source base station transmits a handover request messageto the target base station. The handover request message carries one ormore DRB information items of a source base station at an access networkside and one or more flow QoS information items of a core network side.

In step 2, the target base station receives the handover requestmessage, agrees the handover request, agrees to establish the DRBs inall DRB information items, and generates DRB configuration informationof the target base station according to information carried by thehandover request message. The DRB configuration information of thetarget base station includes a DRB addition modification list. Each termin the DRB addition modification list includes a DRB ID, one or moreflow IDs or QoS IDs associated with a DRB corresponding to the DRB ID,and one or more of the following: PDCP configuration information, RLCconfiguration information and logical channel configuration information.

In step 3, the target base station transmits a handover requestacknowledgement message to the source base station. The handover requestacknowledgement message carries the DRB configuration information of thetarget base station and the DRB addition modification list (each term inthe DRB addition modification list includes the DRB ID and one or moreflow IDs or QoS IDs associated with the DRB corresponding to the DRBID).

In step 4, the source base station receives the handover requestacknowledgement message and transmits an RRC connection reconfigurationmessage to the UE. The RRC connection reconfiguration message carriesDRB configuration information generated by the target base station forthe UE.

In step 5, the UE receives the RRC connection reconfiguration message,and performs, according to the DRB corresponding to each term in the DRBaddition modification list in the DRB configuration information, atleast one of the following: reestablishing a PDCP, reestablishing a RLC,reconfiguring the PDCP according to the PDCP configuration information,reconfiguring the RLC according to the RLC configuration information,and reconfiguring a logical channel according to the logical channelconfiguration information.

An embodiment of the present disclosure provides a handover method. Inthis embodiment, a target base station agrees to establish a part ofDRBs in information of multiple DRBs, and the method includes stepsdescribed below.

In step 1, the source base station transmits a handover request messageto the target base station. The handover request message carriesmultiple DRB information items of a source base station at an accessnetwork side and one or more flow QoS information items of a corenetwork side.

In step 2, the target base station receives the handover requestmessage, agrees the handover request, agrees to establish a part of DRBsin information of multiple DRBs, and generates first DRB configurationinformation according to information carried by the handover requestmessage. The first DRB configuration includes a DRB additionmodification list and a DRB release list.

The target base station puts DRB configuration information correspondingto a first DRB in the DRB information items which the target basestation agrees to establish into the DRB addition modification list, andputs a DRB identifier (DRB ID) corresponding to a second DRB in the DRBinformation items which the target base station does not agree toestablish into the DRB release list.

The DRB addition modification list includes DRB configurationinformation corresponding to a first DRB in information of multiple DRBswhich the target base station agrees to establish. Each DRB informationitem includes a first DRB ID, one or more flow IDs or QoS IDs associatedwith the DRB corresponding to the first DRB ID, and one or more of thefollowing: PDCP configuration information, RLC configuration informationand logical channel configuration information.

In step 3, the target base station transmits a handover requestacknowledgement message to the source base station. The handover requestacknowledgement message carries the first DRB configuration information,a first list of the DRBs which the target base station agrees toestablish (i.e., the DRB addition modification list each term of whichincludes the first DRB ID and one or more flow IDs or QoS IDs associatedwith the DRB corresponding to the first DRB ID) and a second list ofDRBs which the target base station does not agree to establish (i.e.,the DRB release list each term of which includes a second DRB ID).

In step 4, the source base station receives the handover requestacknowledgement message and transmits an RRC connection reconfigurationmessage to the UE. The RRC connection reconfiguration message carriesthe first DRB configuration information.

In step 5, the UE receives the RRC connection reconfiguration message,performs, according to a DRB corresponding to each term in the DRBaddition modification list in the first DRB configuration information,at least one of the following: reestablishing a PDCP, reestablishing aRLC, reconfiguring the PDCP according to the PDCP configurationinformation, reconfiguring the RLC according to the RLC configurationinformation, and reconfiguring a logical channel according to thelogical channel configuration information, and releases the DRBscorresponding to the DRB IDs in the DRB release list according to theDRB IDs in the DRB release list.

An embodiment of the present disclosure provides a handover method. Inthis embodiment, a target base station agrees to establish all DRBs inall DRB information items and changes an association relationshipbetween a DRB and a Qos ID. The method includes steps described below.

In step 1, a source base station transmits a handover request message tothe target base station. The handover request message carries one ormore DRB information items of a source base station at an access networkside and one or more flow QoS information items of a core network side.

In step 2, the target base station receives the handover requestmessage, agrees the handover request, agrees to establish the DRBs ininformation of all DRBs, changes the association relationship betweenthe DRB and the QoS ID (for example, the handover request messageincludes 2 DRBs, i.e., DRB 1 and DRB 2, where DRB 1 is associated withQoS ID 1 and QoS ID 2 and DRB 2 is associated with QoS ID 3 and QoS ID4. After the association relationship is changed, DRB 1 is associatedwith QoS ID 2 and DRB 2 is associated with QoS ID 1, QoS ID 3 and QoS ID4), generates first DRB configuration information according toinformation carrier by the handover request information and the changedassociation relationship between the DRB and the QoS ID, and puts theDRB configuration information corresponding to the DRB in the DRBinformation items which the target base station agrees to establish intoa DRB addition modification list. The first DRB configurationinformation includes the DRB addition modification list. Each DRBconfiguration information in the DRB addition modification list includesa DRB ID, one or more QoS IDs associated with the DRB after theassociation relationship between the DRB and the QoS ID is changed, andone or more of the following: PDCP configuration information, RLCconfiguration information and logical channel configuration information.

In step 3, the target base station transmits a handover requestacknowledgement message to the source base station. The handover requestacknowledgement message carries the first DRB configuration informationand the DRB addition modification list which the target base stationagrees to establish (each term in the DRB addition modification listincludes the DRB ID and one or more flow IDs or QoS IDs associated withthe DRB corresponding to the DRB ID).

In step 4, the source base station receives the handover requestacknowledgement message and transmits an RRC connection reconfigurationmessage to the UE. The RRC connection reconfiguration message carriesthe DRB configuration information of the target base station.

In step 5, the UE receives the RRC connection reconfiguration message,and performs, according to a DRB corresponding to each term in the DRBaddition modification list in the DRB configuration information, atleast one of the following: reestablishing a PDCP, reestablishing a RLC,reconfiguring the PDCP according to the PDCP configuration information,reconfiguring the RLC according to the RLC configuration information,and reconfiguring a logical channel according to the logical channelconfiguration information. In addition, the UE reconfigures theassociation relationship between the DRB and the QoS ID according tofirst DRB configuration information.

An embodiment of the present disclosure provides a handover method. Inthis embodiment, the target base station agrees to establish a part ofDRBs in information of multiple DRBs and changes an associationrelationship between a DRB and a Qos ID. The method includes stepsdescribed below.

In step 1, a source base station transmits a handover request message tothe target base station, where the handover request message carriesmultiple DRB information items of a source base station at an accessnetwork side and one or more flow QoS information items of a corenetwork side.

In step 2, the target base station receives the handover requestmessage, agrees the handover request, agrees to establish a part of DRBsin information of multiple DRBs, changes the association relationshipbetween the DRB and the QoS ID (for example, the handover requestmessage includes 3 DRBs, i.e., DRB 1, DRB 2 and DRB 3, where DRB 1 isassociated with QoS ID 1 and QoS ID 2, DRB 2 is associated with QoS ID 3and DRB 3 is associated with QoS ID 4 and QoS ID 5. The target basestation agrees to establish merely DRB 1 and DRB 2. After theassociation relationship is changed, DRB 1 is associated with QoS ID 1and QoS ID 2, DRB 2 is associated with the QoS ID 3 and QoS ID 5, DRB 3is released and QoS ID 4 is not associated with any DRB), and generatesfirst DRB configuration information according to information carried bythe handover request information. The first DRB configurationinformation includes a DRB addition modification list and a DRB releaselist.

The target base station puts DRB configuration information correspondingto a first DRB in the DRB information items which the target basestation agrees to establish into the DRB addition modification list, andputs a DRB identifier corresponding to a second DRB in the DRBinformation items which the target base station does not agree toestablish into the DRB release list.

The DRB addition modification list includes DRB configurationinformation corresponding to a first DRB which the target base stationagrees to establish in information of multiple DRBs. Each DRBinformation item includes a first DRB ID, one or more QoS IDs associatedwith the DRB corresponding to the first DRB ID after the associationrelationship is changed, and one or more of the following: PDCPconfiguration information, RLC configuration information and logicalchannel configuration information. The DRB release list includes the DRBIDs corresponding to the DRBs which the target base station does notagree to establish.

In step 3, the target base station transmits a handover requestacknowledgement message to the source base station. The handover requestacknowledgement message carries the first DRB configuration information,the DRB addition modification list of the DRBs which the target basestation agrees to establish (each term in the DRB addition modificationlist includes the first DRB ID and one or more QoS IDs associated withthe DRB corresponding to the first DRB ID), the DRB release list of theDRBs which the target base station does not agree to establish (eachterm in the DRB release list include a second DRB ID) and a QoS ID listincluding QoS IDs which are not associated with any of the DRBs in theinformation of multiple DRB s.

In step 4, the source base station receives the handover requestacknowledgement message and transmits an RRC connection reconfigurationmessage to the UE, where the RRC connection reconfiguration messagecarries the DRB configuration information of the target base station.

In step 4 a, the source base station sends the QoS ID list to a corenetwork (the source base station may also operates the target basestation to send the QoS ID list to the core network after the UEsuccessively accesses to the target base station), so that the corenetwork performs relevant response operations.

In step 5, the UE receives the RRC connection reconfiguration message,and performs, according to a DRB corresponding to each item in the DRBaddition modification list in the DRB configuration information, atleast one of the following: reestablishing a PDCP, reestablishing a RLC,reconfiguring the PDCP according to the PDCP configuration information,reconfiguring the RLC according to the RLC configuration information,and reconfiguring a logical channel according to the logical channelconfiguration information. The UE also reconfigures the associationrelationship between the DRB and the QoS ID according to first DRBconfiguration information. The UE release the DRBs corresponding to theDRB IDs according to DRB IDs in the DRB release list.

In the above embodiment, in the 5G system, when the core network and theaccess network adopt different QoS mechanisms and an evolved eNB and a5G base station cannot identify each other's RRC protocol, the methoddescribed above may implement the handover capable of ensuring the QoSon an Xn interface between the evolved eNB and the 5G base station.

An embodiment of the present disclosure provides a storage medium whichis configured to store program codes for executing the steps describedbelow.

A handover request message is transmitted to a target base station,where the handover request message carries information of one or moreDRB information items configured by a source base station for a UE andone or more flow QoS information items configured by a core network sidefor the UE.

A handover request acknowledgement message transmitted by the targetbase station is received, where the handover request acknowledgementmessage carries first DRB configuration information generated by thetarget base station for the UE according to the handover requestmessage.

An RRC connection reconfiguration message carrying the first DRBconfiguration information is sent to the UE, with which the UEconfigures radio resources.

Optionally, in this embodiment, the storage medium may include a U disk,an ROM, an RAM, a mobile hard disk, a magnetic disk, an optical disk oranother medium capable of storing program codes. Optionally, a processorin the source base station executes the following steps according to theprogram codes stored in the storage medium.

A handover request message is transmitted to the target base station,where the handover request message carries one or more DRB informationitems configured by the source base station for the UE and one or moreflow QoS information items configured by the core network side for theUE.

The handover request acknowledgement message transmitted by the targetbase station is received, where the handover request acknowledgementmessage carries the first DRB configuration information generated by thetarget base station for the UE according to the handover requestmessage.

The UE transmits the RRC connection reconfiguration message carrying thefirst DRB configuration information, and the UE configures radioresources by using the DRB configuration information.

One or more modules or one or more steps described above may beimplemented by a general-purpose computing device. They may beconcentrated on a single computing device or distributed on a networkformed by multiple computing devices. Optionally, they may beimplemented by program codes executable by the computing devices, sothat they may be stored in a storage device and executable by thecomputing devices. In some circumstances, the illustrated or describedsteps may be executed in sequences different from those describedherein, or the one or more modules or one or more steps may be made intovarious integrated circuit modules, or each module or step therein maybe made into a single integrated circuit module.

An embodiment provides a schematic diagram illustrating a hardwarestructure of a source base station. With reference to FIG. 10, thesource base station includes:

at least one processor 1000 (FIG. 10 shows one processor 1000 by way ofexample) and a memory 1001. The source base station may further includea communications interface 1002 and a bus 1003. The processor 1000, thememory 1001 and the communications interface 1002 may communicate witheach other via the bus 1003. The processor 1000 may use logicinstructions in the memory 1001 to execute the method executed by thesource base station in the above embodiments.

In addition, the logic instructions in the memory 1001 may beimplemented in the form of a software function unit and, when sold orused as an independent product, may be stored in a computer-readablestorage medium.

As a computer-readable storage medium, the memory 1001 may be used forstoring software programs and computer-executable programs, such asprogram instructions or modules corresponding to the method executed bythe source base station in the above embodiments. The processor 1000runs the software programs, instructions or modules stored in the memory1001 to execute function applications and data processing, that is, toimplement the method executed by the source base station in the aboveembodiments.

The memory 1001 may include a program storage region and a data storageregion. The program storage region may store an operating system and anapplication program required by at least one function, and the datastorage region may store data created depending on use of a terminaldevice. In addition, the memory 1001 may include a high-speed randomaccess memory, and may further include a non-volatile memory.

An embodiment provides a schematic diagram illustrating a hardwarestructure of a target base station. With reference to FIG. 11, thetarget base station includes:

at least one processor 110 (FIG. 11 shows one processor 110 by way ofexample) and a memory 111. The target base station may further include acommunications interface 112 and a bus 113. The processor 110, thememory 111 and the communications interface 112 may communicate witheach other via the bus 113. The processor 110 may call logicinstructions in the memory 111 to execute the method executed by thetarget base station in the above embodiments.

In addition, the logic instructions in the memory 111 may be implementedin the form of a software function unit and, when sold or used as anindependent product, may be stored in a computer-readable storagemedium.

As a computer-readable storage medium, the memory 111 may be used forstoring software programs and computer-executable programs, such asprogram instructions or modules corresponding to the method executed bythe target base station in the above embodiments. The processor 110 runsthe software programs, instructions or modules stored in the memory 111to execute function applications and data processing, that is, toimplement the method executed by the target base station in the aboveembodiments.

The memory 111 may include a program storage region and a data storageregion. The program storage region may store an operating system and anapplication program required by at least one function; and the datastorage region may store data created depending on use of a terminaldevice. In addition, the memory 111 may include a high-speed randomaccess memory, and may further include a non-volatile memory.

An embodiment provides a schematic diagram illustrating a hardwarestructure of a user equipment. With reference to FIG. 12, the userequipment includes:

at least one processor 120 (FIG. 12 shows one processor 120 by way ofexample) and a memory 121. The user equipment may further include acommunications interface 122 and a bus 123. The processor 120, thememory 121 and the communications interface 122 may communicate witheach other via the bus 123. The processor 120 may call logicinstructions in the memory 121 to execute the method executed by theuser equipment in the above embodiments.

In addition, the logic instructions in the memory 121 may be implementedin the form of a software function unit and, when sold or used as anindependent product, may be stored in a computer-readable storagemedium.

As a computer-readable storage medium, the memory 121 may be used forstoring software programs and computer-executable programs, such asprogram instructions or modules corresponding to the method executed bythe user equipment (UE) in the above embodiments. The processor 120 runsthe software programs, instructions or modules stored in the memory 121to execute function applications and data processing, that is, toimplement the method executed by the user equipment (UE) in the aboveembodiments.

The memory 121 may include a program storage region and a data storageregion. The program storage region may store an operating system and anapplication program required by at least one function; and the datastorage region may store data created depending on use of a terminaldevice. In addition, the memory 121 may include a high-speed randomaccess memory, and may further include a non-volatile memory.

INDUSTRIAL APPLICABILITY

A handover method and apparatus may solve the problem that the QoSmechanism adopted by a core network and the QoS mechanism adopted by anaccess network are different when the base station is being handed over.

1. A handover method, comprising: transmitting a handover requestmessage by a source base station to a target base station, wherein thehandover request message carries one or more data radio bearer (DRB)information items and one or more flow quality of service (QoS)information items; and receiving, by the source base station, a handoverrequest acknowledgement message from the target base station, whereinthe handover request acknowledgement message carries a DRB configurationinformation for a user equipment (UE) according to the handover requestmessage.
 2. The method according to claim 1, wherein each flow QoSinformation item comprises identifier information for indicating theflow quality of service information item, wherein the identifierinformation comprises a flow identifier (flow ID).
 3. The methodaccording to claim 1, wherein each flow QoS information item comprises aquality of service (Qos) rule, wherein the QoS rule comprises aguaranteed flow bit rate, a maximum flow bit rate, a flow priority level(FPL), and a reflective QoS indication.
 4. The method according to claim2, wherein each DRB information item comprises: a DRB identifier (DRBID), a packet data convergence protocol (PDCP), a radio link control(RLC) and a configuration parameter of a logical channel.
 5. (canceled)6. A handover method, comprising: receiving, by a target base station, ahandover request message from a source base station, wherein thehandover request message carries one or more data radio bearer (DRB)information items and one or more flow quality of service (QoS)information items; generating a DRB configuration information by thetarget base station for a user equipment (UE) according to the handoverrequest message.
 7. (canceled)
 8. The method according to claim 6,wherein the DRB configuration information comprises: a DRB identifier(ID), packet data convergence protocol (PDCP) configuration information,radio link control (RLC) configuration information and logical channelconfiguration information. 9-14. (canceled)
 15. A handover apparatus,applied to a source base station, comprising: a processor configured to:transmit a handover request message to a target base station, whereinthe handover request message carries one or more DRB information itemsand one or more flow QoS information items; and receive a handoverrequest acknowledgement message from the target base station, whereinthe handover request acknowledgement message carries a DRB configurationinformation for a user equipment (UE) according to the handover requestmessage.
 16. The apparatus according to claim 15, wherein each flow QoSinformation item comprises identifier information for indicating theflow quality of service information item, wherein the identifierinformation comprises a flow identifier (flow ID).
 17. A handoverapparatus, applied to a target base station, comprising: a processorconfigured to: receive a handover request message from a source basestation, wherein the handover request message carries one or more dataradio bearer (DRB) information items and one or more flow quality ofservice (QoS) information items; generate a DRB configurationinformation for a user equipment (UE) according to the handover requestmessage. 18-21. (canceled)
 22. The method according to claim 1, furthercomprising: transmitting a radio resource control (RRC) connectionreconfiguration message carrying the DRB configuration information bythe source base station to the UE.
 23. The method according to claim 4,wherein each DRB information item comprises the flow ID associated withthe DRB corresponding to the DRB ID.
 24. The method according to claim6, further comprising: transmitting a handover request acknowledgementmessage carrying the DRB configuration information by the target basestation to the source base station.
 25. The method according to claim 6,wherein each flow QoS information item comprises identifier informationfor indicating the flow quality of service information item, wherein theidentifier information comprises a flow identifier (flow ID).
 26. Themethod according to claim 6, wherein each flow QoS information itemcomprises a quality of service (Qos) rule, wherein the QoS rulecomprises a guaranteed flow bit rate, a maximum flow bit rate, a flowpriority level (FPL), and a reflective QoS indication.
 27. The apparatusaccording to claim 15, wherein each flow QoS information item comprisesa quality of service (Qos) rule, wherein the QoS rule comprises aguaranteed flow bit rate, a maximum flow bit rate, a flow priority level(FPL), and a reflective QoS indication.
 28. The apparatus according toclaim 16, wherein each DRB information item comprises: a DRB identifier(DRB ID), a packet data convergence protocol (PDCP), a radio linkcontrol (RLC) and a configuration parameter of a logical channel. 29.The apparatus according to claim 28, wherein each DRB information itemcomprises the flow ID associated with the DRB corresponding to the DRBID.
 30. The apparatus according to claim 15, wherein the processor isfurther configured to: transmit a radio resource control (RRC)connection reconfiguration message carrying the DRB configurationinformation by the source base station to the UE.
 31. The apparatusaccording to claim 17, wherein the DRB configuration informationcomprises: a DRB identifier (ID), packet data convergence protocol(PDCP) configuration information, radio link control (RLC) configurationinformation and logical channel configuration information.
 32. Theapparatus according to claim 17, wherein the processor is furtherconfigured to: transmit a handover request acknowledgement messagecarrying the DRB configuration information by the target base station tothe source base station.
 33. The apparatus according to claim 17,wherein each flow QoS information item comprises identifier informationfor indicating the flow quality of service information item, wherein theidentifier information comprises a flow identifier (flow ID).
 34. Theapparatus according to claim 17, wherein each flow QoS information itemcomprises a quality of service (Qos) rule, wherein the QoS rulecomprises a guaranteed flow bit rate, a maximum flow bit rate, a flowpriority level (FPL), and a reflective QoS indication.